nixos: use uniq in the type of system.build#155963
Conversation
|
I didn't know that it did that, but Regarding the submodule, see blocked pr #155883. |
|
Sounds good, I looked at all definitions of |
`unspecified` will happily concatenate strings together from two unrelated modules, causing spurious errors (see NixOS#155925).
a25031a to
1147d72
Compare
anything instead of unspecified in the type of system.builduniq in the type of system.build
|
@ofborg test grub systemd-boot login |
|
Before |
|
OfBorg evaluates fine. The error on arm is caused by a build failure after eval, caused by a full disk. I hope not too many collisions exist out there, because they're about to be discovered -- well, except for the fraction of users that turned away because they couldn't figure out why their config or module didn't apply because of the silent collisions. Sad. Let's fix this problem for current and future configs. Merging. |
unspecifiedwill happily concatenate strings together from two unrelated modules, causing spurious errors (see #155925).Ideally we could make system.build a submodule with a few distinguished options like installBootLoader, but I don't think this is necessary right now.
I've tested this by running a vm with
build-vm-with-bootloader.